SSH: refactor Jupyter init script to use better Spark session initialization flow#4645
Merged
SSH: refactor Jupyter init script to use better Spark session initialization flow#4645
Conversation
Collaborator
|
Commit: 1a6d44a
25 interesting tests: 8 FAIL, 7 SKIP, 6 RECOVERED, 2 flaky, 1 KNOWN, 1 BUG
Top 21 slowest tests (at least 2 minutes):
|
cdb52e9 to
1a6d44a
Compare
anton-107
approved these changes
Mar 5, 2026
Collaborator
|
Commit: 6357294
52 interesting tests: 23 RECOVERED, 22 FAIL, 4 flaky, 1 KNOWN, 1 BUG, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Why
We've had different path for serverless spark before, where we didn't use UserNamespaceInitializer, which was not ideal, since the global jupyter scope for serverless and dedicated was different because of that.
The reason to use Databricks Connect on dedicated cluster is to expose the same spark connect API in all environments, avoiding compatibility issues. Local spark has access to some internal jvm APIs, which are not available in spark connect mode, but the rest is the same.
Tests
Manually and existing e2e tests